/**
 * Work with standard transactions.
 *
 * Standard transactions provide so-called "1.5 phase commit".  We can
 *   ensure that work is never lost, but there is a chance of confirmations
 *   being lost, so that messages may be resent.  Applications that use
 *   standard transactions must be able to detect and ignore duplicate
 *   messages.
 *
 * @name Tx
 * @exports Tx as api.Tx
 * @class
 */


/**
 * Confirm transaction mode.
 *
 * This method confirms to the client that the channel was successfully
 *     set to use standard transactions.
 *
 * @name Tx#selectOk
 * @event
 * 
 */

/**
 * Confirm a successful commit.
 *
 * This method confirms to the client that the commit succeeded.
 *     Note that if a commit fails, the server raises a channel exception.
 *
 * @name Tx#commitOk
 * @event
 * 
 */

/**
 * Confirm a successful rollback.
 *
 * This method confirms to the client that the rollback succeeded.
 *     Note that if an rollback fails, the server raises a channel exception.
 *
 * @name Tx#rollbackOk
 * @event
 * 
 */



/**
 * Select standard transaction mode.
 *
 * This method sets the channel to use standard transactions.  The
 *     client must use this method at least once on a channel before
 *     using the Commit or Rollback methods.
 *
 * @name Tx#select
 * @function
 * 
 */

/**
 * Commit the current transaction.
 *
 * This method commits all messages published and acknowledged in
 *     the current transaction.  A new transaction starts immediately
 *     after a commit.
 *
 * @name Tx#commit
 * @function
 * 
 */

/**
 * Abandon the current transaction.
 *
 * This method abandons all messages published and acknowledged in
 *     the current transaction.  A new transaction starts immediately
 *     after a rollback.
 *
 * @name Tx#rollback
 * @function
 * 
 */

